-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
data source/service: Add data source for service #16640
Conversation
ae9ea4e
to
d4388a9
Compare
Let's clear up #16641 (comment) before continuing here. We may also want to clarify the attributes better since this should not be EC2 specific and support forward and reverse DNS information. |
d4388a9
to
f9cd315
Compare
b47c1fc
to
93e5fe9
Compare
Pull request #21306 has significantly refactored the AWS Provider codebase. As a result, most PRs opened prior to the refactor now have merge conflicts that must be resolved before proceeding. Specifically, PR #21306 relocated the code for all AWS resources and data sources from a single We recognize that many pull requests have been open for some time without yet being addressed by our maintainers. Therefore, we want to make it clear that resolving these conflicts in no way affects the prioritization of a particular pull request. Once a pull request has been prioritized for review, the necessary changes will be made by a maintainer -- either directly or in collaboration with the pull request author. For a more complete description of this refactor, including examples of how old filepaths and function names correspond to their new counterparts: please refer to issue #20000. For a quick guide on how to amend your pull request to resolve the merge conflicts resulting from this refactor and bring it in line with our new code patterns: please refer to our Service Package Refactor Pull Request Guide. |
All of these items have been addressed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! 🚀
One comment
if _, ok := d.GetOk("service_id"); !ok { | ||
d.Set("service_id", endpoints.Ec2ServiceID) | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not a fan of adding a default here: if the practitioner is looking up a specific service, they should specify it.
This functionality has been released in v4.1.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
Can we also have Here is where we need it - https://github.com/terraform-aws-modules/terraform-aws-iam/pull/189/files/aa480435226ed9f9b4fc4a247ee9f6cabe1938ad#diff-eaa3db68ce5b0e6250b8b884997ba06f95e89312aee5c8bac7d9b703c7732257R507 |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
Closes #16641
Output from acceptance tests (
us-west-2
):Output from acceptance tests (GovCloud):